[fix](query-cache) include variant subcolumn path in query cache digest#61709
Merged
924060929 merged 1 commit intoapache:masterfrom Mar 25, 2026
Merged
[fix](query-cache) include variant subcolumn path in query cache digest#61709924060929 merged 1 commit intoapache:masterfrom
924060929 merged 1 commit intoapache:masterfrom
Conversation
Different variant subcolumn queries (e.g. data['int_1'] vs data['int_nested']) were generating the same cache digest because normalizeSelectColumns() only used the base column name. This caused query cache to return wrong results when different subcolumns of the same variant column were queried. Fix: include the variant subcolumn path in the normalized select column name so that different subcolumns produce different cache digests.
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
morrySnow
approved these changes
Mar 25, 2026
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 26546 ms |
TPC-DS: Total hot run time: 168736 ms |
Contributor
FE UT Coverage ReportIncrement line coverage |
github-actions bot
pushed a commit
that referenced
this pull request
Mar 25, 2026
…st (#61709) Different variant subcolumn queries (e.g. data['int_1'] vs data['int_nested']) were generating the same cache digest because normalizeSelectColumns() only used the base column name. This caused query cache to return wrong results when different subcolumns of the same variant column were queried. Fix: include the variant subcolumn path in the normalized select column name so that different subcolumns produce different cache digests.
github-actions bot
pushed a commit
that referenced
this pull request
Mar 25, 2026
…st (#61709) Different variant subcolumn queries (e.g. data['int_1'] vs data['int_nested']) were generating the same cache digest because normalizeSelectColumns() only used the base column name. This caused query cache to return wrong results when different subcolumns of the same variant column were queried. Fix: include the variant subcolumn path in the normalized select column name so that different subcolumns produce different cache digests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Different variant subcolumn queries (e.g. data['int_1'] vs data['int_nested']) were generating the same cache digest because normalizeSelectColumns() only used the base column name. This caused query cache to return wrong results when different subcolumns of the same variant column were queried.
Fix: include the variant subcolumn path in the normalized select column name so that different subcolumns produce different cache digests.
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)